Meridian Enterprise can be deployed in virtualized, high availability infrastructures like VMware or Microsoft Hyper-V in a Windows Server failover cluster environment or similar. By doing so, the underlying IT architecture provides high availability for Meridian Enterprise. Other scenarios for partial high availability or switchover are also possible.
For example, using VMware vSphere Replication, a production Meridian Enterprise server running on a virtual machine can be replicated to one or more copies in real time. If the production server fails, services can be switched over to a shadow server with minimal effort and time loss.
Meridian Explorer runs on Microsoft and Oracle systems for storing, managing, and serving documents and their metadata. It can thereby claim high availability when the Microsoft SQL Server or Oracle database and IIS web server are run in high availability clusters.
If a virtualized environment is not an option, certain components of Meridian Enterprise can achieve high availability with the aid of other infrastructure or 3rd party tools.
The Meridian Enterprise license server supports redundancy when the concurrent license model is used. This means that one license server can request licenses that are registered at another license server.
For example, assume that license servers A and B located at separate sites each have 50 licenses registered. The pool of 100 licenses can be freely divided between the two sites. Site A can use 75 licenses and site B can use 25. However, if the connection between the license servers is lost, each site will be limited to their own 50 licenses. This license pooling is only supported by concurrent licenses. It is not supported by named licenses since each user must claim their own license and the licenses cannot be shared.
Related concepts
About Meridian deployment strategies
Understanding the single server strategy
Understanding the multiple server strategy
Understanding the workgroup model